System and method for single sign on process for websites with multiple applications and services

ABSTRACT

A system and method for integrating the Internet front end-sign on processes of the various systems of a financial institution which allows a customer to view and access its various financial accounts with the institution. 
     During the initial sign up for the online access to its accounts, a customer creates his/her User ID and password online during the same session. Once the customer has signed on (password) and verified ownership of at least one account, the system displays all of the customer&#39;s accounts that are available for access via the Internet website. The online ownership verification uses only a single account of the customer and the ownership verification criteria associated with the account. The account used for verifying a customer is first determined based on the accounts selected by the customer for accessing online. From the selected accounts, the system of the present invention creates a verification hierarchy with respect to the accounts. When determining the verification to use for the single ownership verification, the present invention selects the account from the hierarchy with the most stringent requirements.

FIELD OF THE INVENTION

The present invention generally relates to systems and methods forproviding access to financial accounts and more particularly to systemsand methods for sign up, log on and ownership verification proceduresfor providing access to a plurality of financial accounts over theInternet.

BACKGROUND OF THE INVENTION

As with most industries, the Internet has significantly affected the wayin which the financial industry communicates with its customers. Mostsignificantly, major financial institutions have found providing theircustomers with online access to their accounts both desirable, costeffective, and indeed necessary to remain competitive.

The financial industry faces special hurdles in providing online accessto customer's accounts due to the very nature of the accounts beingaccessed. The account information maintained by financial institutionsis probably the most important and private personal information that aninstitution can hold for a person. Accordingly, controlling access tothis information is one of the most significant duties that must beperformed by a financial institution.

Most large financial institutions have various divisions that separatelyhandle different types of accounts for their customers. For example onedivision maintains personal banking accounts (e.g., checking andsavings), another division handles mortgages, while yet other divisionsare responsible for maintaining credit card and investmentsrespectively. Furthermore, each of the types of accounts is typicallygoverned by a different set of regulations. For example, the rules thatgovern a checking account are completely different from the rules thatgovern an investment account. For these reasons as well as others, thedivisions within a financial institution have traditionally operatedindependently, each developing their own systems and methods foroperating their particular line of business. Unfortunately, thedevelopment of these separate systems has included the separatedevelopment of Internet interfaces for communicating with customers.These separate interfaces are confusing to the customer and do notprovide a uniform appearance of the financial institution to itscustomers.

Some financial institutions have attempted to solve this problem byprovided links on a single institution web page that lead to the varioussystems of the divisions of the institution. One significant problemthat persists is that a customer must separately sign up, verifyownership, and log onto the separate systems, providing separatepasswords and separate verifications of ownership.

Other institutions have solved this problem by requiring ownership of aspecific type of account (e.g., a checking account) and manually linkingor otherwise associating the privileges of access of all other types ofaccounts to the required account. This reduces the number of customerswith access to their account information and transaction capability tothe customer base of the required account.

It is therefore an object of the present invention to solve the problemsof the prior art in a system and method that requires only a single signup, verification and single ID for a website that includes multipleapplications and multiple services.

SUMMARY OF THE INVENTION

The system and method of the present invention integrate the Internetfront-end log on processes of all of the various systems of theinstitution. In this manner, the present invention provides a singularway for a customer to identify that they are a customer of theinstitution, regardless of the application or services that the customerends up using on the Internet website of the institution. In a preferredembodiment, the single sign on processes are used for customers of afinancial institution to view and conduct transactions with respect totheir accounts with the institution. These accounts include but are notlimited to checking and savings accounts, mortgages, credit cardaccounts, investment accounts, online trading, auto loans and leases,home equity loans, personal loans, trust accounts, 401k accounts andinsurance accounts.

During the initial sign up for the online access to its accounts, acustomer creates their User ID and password online during the samesession. There is no need for the institution to mail the User ID orpassword to the customer. This same sign up process allows the customerto provide verification of ownership to obtain rights to information andservices available online for their accounts. Once the customer haslogged on (password) and verified their ownership of at least oneaccount, the system displays all of the customer's accounts that areavailable for access via the Internet website. In addition to signing upexisting customers, the present invention permits the creation ofnon-authenticated IDs for potential customers to use (or for customersto use for non-account access). For example, a non-customer can beprovided access to online account opening services, pre-populatingapplication data with their account information saving accountapplication data, viewing status of new account application, and savingcalculator and financial planning data.

A significant feature of the present invention is the onlineverification of ownership by a customer. Based on identifyinginformation entered for one account, the list of all accounts owned bythe customer is presented to the customer to choose which accounts theywant to access online. Online ownership verification uses only a singleaccount of the customer and the verification criteria associated withthe account. A customer may have several accounts with the institution,but may only choose to view one or two online (although the customer maychoose to view all the accounts). From the selected accounts, the systemof the present invention creates a verification hierarchy with respectto the accounts. The hierarchy places the selected accounts in the orderof difficulty of the verification. When determining the verificationquestions to use for the single account, the present invention selectsthe account from the hierarchy with the most stringent requirements. Theverification of ownership required for the different accounts might beless or more stringent based on the risk of the account and the lack ofaccessibility of verification data to the general public. For example,the verification required for access to credit card or deposit accountsis the most stringent, requiring a code only available on the back ofthe card or a PIN known only to the customer. Once the account that ishighest in the hierarchy is verified, all other accounts that are equalor lower in the hierarchy are considered verified as well.

Once a customer has signed up and logged on, the present inventiondisplays all customer accounts that the customer has selected forviewing (including account balances) on an account summary page. Thisaccount summary page allows the customer to then navigate to the line ofbusiness site to see more details or transact using the account. Oncesigned up for the online process, customers are able to add additionalaccounts online once they are available online or once a customeracquires a product. This process may not require additional verificationof ownership, depending on where the new product falls in theverification hierarchy.

In subsequent logons to the system, the present invention allowscustomers to re-identify themselves to see a forgotten ID, and tore-verify themselves so they can recreate a password if a password isforgotten. The present invention allows the customer to create answersto challenge questions that only the user should know the answer to. Forexample, a challenge question could be, “what model was your firstcar?”. The answers to the challenge questions are stored in the systemfor future use if the user forgets his password. If the situation occursthat the user does forget his password, he is presented with thechallenge questions to which he previously provided the answers. If theuser successfully answers the challenge questions, he is allowed accessto the system (and is allowed to change his password).

In addition to the challenge questions, the user is also able to create“cue” questions. The cue questions provide the user with a hint as tothe user's selected password. For example, if the user selects the nameof his dog as his password, the customer can create a cue question suchas “What is your dog's name.” If the user forgets his password, he isfirst presented with the cue question to see if the user can recollectthe password. If the cue question does not jog the user's memory, he isthen presented with the challenge questions that allow the user tore-identify himself to the system.

The present invention is not limited to providing access to personalaccounts and is equally applicable to business accounts. Businesscustomers can use the system for online enrollment, fulfillment andownership verification. This includes customers who want to see bothpersonal and business accounts under one ID and password. The businessowner may be a sole proprietor (using a social security number), abusiness owner or partner (using a tax identification number (TIN)), ora multiple business owner (multiple TINs). Furthermore, the systemallows a tiered authority structure where an owner of an account can setup and authorize access to the same or lesser levels of authority tonon-owners of the accounts (e.g., spouses or employees). This allows setup and monitoring of sub-IDS for consumers as well as businesses.

Another significant feature of the present invention is its ability toallow the customer to self-service their sign up, logon, and forgottenID or password processes without having to contact customer service orwait for information to be given or sent to them.

The present invention provides ease of use by the customer since thecustomer does not need to duplicate work such as inputting his or hersocial security number, account number and other personal or accountinformation a number of different times to either sign up for access orto logon to see their accounts. The ability for the customer to use“self-service” sign up and logon failure procedures eliminates orminimizes customer and back office support for fulfillment (e.g.,issuing IDs, passwords, and reissued passwords). The single sign on IDand password that allows access to all of the customer's accountsprovides speed of fulfillment, ease of use and reduced customer supportfor issued or forgotten IDs and passwords. The ability for customers tosee all of their accounts with one logon eases the customer experienceand enhance customer retention, as well as enhancing cross-sell andup-sell efforts.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purposes of illustrating the present invention, there is shownin the drawings a form which is presently preferred, it being understoodhowever, that the invention is not limited to the precise form shown bythe drawing in which:

FIG. 1 illustrates the hardware of the system of the present invention;

FIG. 2 depicts an overview of the sign up and log on processes of thepresent invention;

FIG. 3 shows a detailed flow of the sign up process; and

FIG. 4 illustrates the authentication process.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to the drawing figures in which like reference numbersrefer to like elements, there is shown in FIG. 1 a diagram of thehardware elements of the system of the present invention, designatedgenerally as “100”.

System 100 illustrates the system of the present invention that allowscustomers 110 to use a single sign on procedure to obtain access to aplurality of their accounts residing on the systems 190-196 fordifferent lines of business in the institution. Customers 110 use theirworkstations 110 to connect to system 100 through a communicationnetwork 115. In a preferred embodiment, the network 115 is the publicInternet but can be any other communication connection such as a directdial up line or a third party value add network. Customer workstations110 are comprised of any platform capable of running an Internet webbrowser or similar graphical user interface software. Examples ofsuitable web browsers include Microsoft's Internet Explorer™ andNetscape's Communicator™. The platform for user workstations 110 canvary depending on the needs of its particular user and includes adesktop, laptop or handheld personal computer, personal digitalassistant, web enabled cellular phone, web enabled television, or even aworkstation coupled to a mainframe computer.

In the preferred embodiment, customer workstations 110 communicate withsystem 100 using the Transmission Control Protocol/Internet Protocol(TCP/IP) upon which particular subsets of that protocol can be used tofacilitate communications. Examples include the Hypertext TransferProtocol (HTTP), data carrying Hypertext Mark-Up Language (HTML) webpages, Java and Active-X applets and File Transfer Protocol (FTP). Dataconnections between customer workstations 110 and data communicationnetwork 115 can be any known arrangement for accessing a datacommunication network, such as dial-up Serial Line InterfaceProtocol/Point-to-Point Protocol (SLIP/PPP), Integrated Services DigitalNetwork (ISDN), dedicated leased-line service, broadband (cable) access.Digital Subscriber Line (DSL), Asynchronous Transfer Mode (ATM), FrameRelay or other known access techniques. Web servers 120 are coupled todata communication network 115 in a similar fashion. However, it ispreferred that the link between the web servers 120 and datacommunication network 115 be arranged such that access to web servers120 is always available.

It should be noted that although customer workstations 110 and webservers 120 are shown as each coupled to a single data communicationnetwork 115, this arrangement is shown merely for the convenience ofaiding explanation of the present invention and is not limited to such.For example, data communication network 115 can be the Internet or otherpublic or private network comprised of multiple communication networks,coupled together by network switches or other communication elements.Between the communication network 115 and the web servers 120 of system100 is a “soft” firewall 117. Soft firewall 117 is firewall that iserected using only software techniques (as opposed to firewall describedbelow).

Web servers 120 are comprised of one or more central processing unitscoupled to one or more databases (not shown). In addition, web servers120 further comprise a network interface (not shown) to couple theprocessor to data communication network 115, and include provisions fora web site or other technology which can create a network presence fromwhich the provider of web servers 120 can interact with customerworkstations 110. Technologies including hardware and software forestablishing web sites such as an Internet web site are known.

Web servers 120 can be comprised of any suitable processor arrangementdesigned to accommodate the expected number of users and transactionsfor the particular system in which these elements will be implemented(hence the illustration of three web servers 120 in FIG. 1). Knownsoftware languages and database technologies can be used to implementthe described processes. The databases and programmatic code used by webservers 120 are stored in suitable storage devices within, or which haveaccess to, web servers 120. The nature of the invention is such that oneskilled in the art of writing computer executable code (software), wouldbe able to implement the described functions using one or more popularcomputer programming languages such as “C++”, Visual Basic, Java orHTML.

The web servers 120 are each coupled, through a separate firewall 125,to application server 130. The firewall 125 is comprised of bothhardware and software components as well known in the art. Firewall 125is required to protect the confidential information contained in system100 illustrated below firewall 125 in FIG. 1. As implied by its title,the application server 130 is where the applications employed by the webservers 120 reside. Coupled to the application server 130 is a database135. Aside from other data, the customer profiles containing the userIDs, passwords and relationship and profile data is stored. Although notshown, database 135 cart include a suitable database management systemprocessor which operates thereon. In addition, although database 135 isshown as a separate entity in FIG. 1, it is contemplated that database135 can be implemented as part of a storage device within theapplication server 130, or can even be coupled to application server 130across a communication link. Database 135 is preferably amultidimensional database that is analyzed using on-line analyticalprocessing (OLAP) tools.

The application server 130 is coupled to the systems of the variouslines of business 190-196 through a communication server 140 and adelivery processor 145. As described below, if a customer wishes to viewmore detailed information regarding an account, or wishes to conductsome transactions, the user is coupled to the specific line of businesssystem 190-196 that maintains the desired account. The communicationserver 140 and the delivery processor 145 together they serve as amiddleware component for communication between the application server130 and the line of business systems 190-196.

FIG. 2 illustrates an overview of the sign up and log on processes ofthe present invention. In step 200 a customer is presented with anup-front filter asking them to define themselves as a business,personal, both business and personal, or if they are not a customer.Prior to the customer continuing in the process, a warning is presentedto the customer with respect to the dual signature limitation forbusiness customers. Based on the self-section, the customer is presentedwith an explanation in regard to the linking of personal and businessaccounts, the single signer requirement, and the necessity of signing upbusiness accounts first.

For business customers, system 100 collects business name, individualname, email, TIN, one account number and type. Then, system 100identifies that the business customer exists based on a CustomerIdentification File (CIF) contained in database 135 (see FIG. 1) bymatching on TIN and account number.

For personal customers, system 100 collects first and last name, e-mailaddress, social security number, and account number and type. System 100then uses the social security number and account number to identify thatthey exist.

In step 205 the customer selects his own User ID and Password. The UserID is preferably 8-20 characters in length, while the password ispreferably 6-10 characters in length with one alphanumeric and onenumeric character. The password is also preferably case insensitive.This ID and password is created whether or not the customer wassuccessfully identified in the previous step. If the customer wassuccessfully identified, they will be allowed to continue the sign upprocess. If system 100 was unable to identify the customer, the customeris requested to call customer service to identify the problem and tocontinue the sign up process via the call center. Because the customerhas already selected their ID and password, the call centerrepresentative is able to easily identify the customer using the ID andthe customer does not have to wait for fulfillment of an ID and passwordin the mail and is able to logon to the system after completing the callwith the customer service representative.

After creating the User ID and password, the customer is presented withthe option to select challenge questions, which as described below,enables them to reset their passwords online, by themselves, in theevent the customer forgets the password selected. In step 210, thecustomer is then presented with an online legal agreement that must beaccepted prior to the customer continuing. The online legal agreementcontains all of the terms and conditions of the customer's use of system100. For those customers who were set up via the call center, this legalagreement is presented to them upon logging on for the first time.

In step 215, the customer is shown all of his/her accounts (includingbusiness accounts if applicable) that he/she has with the institution.The account information is presented to the customer based on datacontained in the customer's CIF profile. After the accounts have beenpresented to the customer, the customer is given the option to viewthese accounts using system 100. In addition to the accounts thecustomer can view, the customer is the customer is shown all services(e.g., tax, payroll, wire transfer, and electronic billing services) inwhich the customer is able to participate.

In step 235, the customer is presented with a set of verification ofownership questions based on the accounts the customer has selected toaccess. As previously described, the ownership verification procedurefollows a hierarchy where the customer is asked questions based on the“highest level” product he has selected to access. In a preferredembodiment, for personal customers, credit card accounts are the highestlevel, followed by deposit, loans, investments, and mortgages. Allproducts are represented and have an assigned level within theverification hierarchy. If the customer passes verification, he/she hascompleted the sign up process, is presented with a screen confirmingwhich accounts they can access and can proceed to logon to access theiraccounts. If the customer fails verification—for example, due to missinginformation on the host systems—the customer can “drop down” to the nextaccount type on the hierarchy or contact Customer Service forassistance. Upon successfully passing the lower level verificationquestions, the customer will have rights to access those accounts andany accounts lower in the hierarchy, but will not have the rights toaccess the accounts that were represented by the failed, higher level ofverification questions.

In the initial sign-up process and during subsequent log ons, system 100checks to ensure the customer has a browser that provides adequatesecurity measures (e.g., encryption). This check also validated that thecustomer can receive cookies and has javascript enabled on their browsersettings. This security is required because of the sensitive financialnature of the information being provided to the customer. In a preferredembodiment, the customer's browser supports 128-bit encryption. When theuser clicks on ‘Sign Up’ or ‘Log On’ from the main welcoming screen ofsystem 100, or when the user attempts to access a protected resource,the browser check is completed. If the user's browser is detected withless-than-128-bit encryption the user is given the option to downloadthe latest browser/patch or given instructions on how to correct hissituation. In addition, a self-check function is provided for customerswhen learning about system requirements for signing up.

FIG. 3 illustrates the detail of the sign up process. The sign upprocedures allow a new user to create an online User ID and Password. Inaddition, if this user is also a customer of the financial institution,he/she can register for access to his accounts. As previously described,the present invention operates, in a Graphical User Interface (GUI)environment, in which the users are presented with a series of screens.The screens allow the system 100 to both elicit information from theuser (e.g., selections) and present information to the user (e.g.,account summaries). In the sign-up process, the first screen presentedto the user is filter screen that asks the customer which accounts hewould like to access (see step 300). In a preferred embodiment, thechoices on this filter screen include: Personal Only, Small BusinessOnly, Both Personal and Small Business using one User ID, Both Personaland Small Business using two User ID's, and “I do not have accounts withthe institution”. Depending on the selection, the user is presented witha brief description of the Sign Up process and features and benefitsinformation. The filter pages are used to determine whether the user ispresented with the Personal, Small Business, or Prospect Identificationquestions.

In step 305, the user identifies himself or herself to system 100.Depending on the entry point, the identification process differsslightly. A user coming for account access is asked if they are tryingto access their personal, small business, or both accounts. If theyselect personal, they will see a personal identification screen. If theypick either Small Business or Both, they will start at the SmallBusiness identification screen.

Each of the identification screens prompt the user for informationsufficient to retrieve the customer's information from the CIF. Thisinformation includes the Social Security Number (SSN) for access topersonal accounts, the Taxpayer Identification Number (TIN) for accessto business accounts, the customer's account number and account type,the user's first and last name and email address. The email addressportion of the input screen for identification also has a check box toallow users to opt-in for marketing email messages.

Additionally, customers are requested to choose a country from adrop-down with a list of countries. The entry for the United States isthe default and other countries are preferably listed alphabetically. Ifthe user chooses the United States, he is also prompted to enter a zipcode. This information is collected to understand which regulatoryrequirements under which customers may be covered if they choose toapply for a product line.

The account type field is populated from a selection by the user from adrop-down list box of account types. The presentation of this dropdownlist varies depending on the type of user. Users coming through anaccess point other than signing up for account access are presented witha complete list of all account types that are on CIF. In a preferredembodiment, the following are the types of accounts accessible fromsystem 100: Credit Card; Mortgage; Checking; Savings; Overdraft Line ofCredit; Credit-on-Demand; Certificates of Deposit (CDs); Money MarketAccount (MA); IRA—CD; IRA—Savings; IRA—MMA; Investments; Personal Loans;Auto Loans; Home Equity loans and Line of Credit; and Insurance.

The user iterates through the identification screen until all mandatoryfields are entered in the proper format. Next, the social security orTIN and the account number are used to query the CIF for a match. If aCIF# record is found for this user, system 100 checks to see if a userID associated with this CIF# already exists in the system 100. If such auser ID is already associated with the CIF for the customer, system 100displays the ID to the user and explains that multiple ID's are notallowed. In this case, the user is given the option to Log On with thisID (see below) and explain to him that if he was trying to “add” or“show” an account, he should Log On and use the Show/Hide Accounts linkto accomplish this. If the customer never finished the Sign Up processpreviously begun, the customer is provided a link to Log On and thecustomer is presented with the screen applicable to their next step inthe process. System 100 also asks the user if he has forgotten hispassword and provides a link that takes the user to LogOn/Re-authenticate flow (se below).

The process varies slightly for prospects (users with no accounts withthe financial institution). For a prospect, the user is prompted forFirst and Last Name, Email address (required), Company Name, and anindicator of their interest (personal products, small business products,or both). This user is automatically passed to the Create ID/Password,step 310, since there is no need to perform a CIF match.

In step 310, the user is prompted to Create a user ID, a password andchallenge questions. Regardless of whether the user is identified on theCIF, the user is allowed to create an ID and password that are added tothe database of system 100. Prospects (users without current accounts)are allowed to establish a user ID and password in order to facilitateSign Up at a later time or to access non-account features, such assaving data to a calculator or application or personalizing a financialutility page. The user is created in the system by adding the ID,password and email address to the database. If the user has beenidentified as a customer with current accounts, the customer's CIFnumber is also stored in the database with the ID and password.

At this point in the sign up process, the user is also prompted toselect and answer challenge questions. These challenge questions replacethe prior art method of re-verifying using account information. The userselects one question from each of three drop down lists and completesthe answers. Users that have passed the CIF match (i.e. customers) havethe option to opt-out of challenges. If they choose to do so, they willnot be able to re-verify online and create a new password. They wouldhave go through the customer service center of the institution and a newpassword is mailed to them. As previously described, the challengequestions are personal in nature, of a type that only the user would beable to answer them (e.g., what was your first grade teacher's name).

After the user completes the user ID, password and challenge questionfields, the customer is presented with a verification screen where shehas the opportunity to go back and change the user ID, password, and/orchallenges if they are not correct. If the user is not found on the CIFand the user attempted a CIF match, he will be assigned a roleindicating he has not been identified as a customer of the institution(denoted as an UNAUTH user). The treatment of these users is the same asprospects. The Sign Up process ends at this point for users not found onthe CIF. They are presented with a dynamic customer support screen.

In step 315, the user is presented with the legal agreement governingthe user's access to system 100. All users creating a user ID andpassword have to accept the legal agreement. This is equally true forprospects and customers that have both passed or failed the CIF match.Since these users will have other functionality at the site, they allneed to accept the legal agreement. The user is presented with the legalagreement and has the option to select “I Agree” or “I Disagree” or“Print”. If the user rejects the disclosure, she is notified that shecannot continued with the sign up process and is presented with theoption to view it again. If the user accepts the disclosure, the sign upprocess continues.

After the user accepts the legal agreement, there is a decision pointbefore proceeding to the next step. If the customer was coming from aprocess other than, signing up for account access, the user will beprompted to Log On. After successfully logging on, the user is returnedto the process that brought him to Sign Up. If the user is signing upfor account access, the user will continue with show/hide functionality.

As part of the sign up process, the user is prompted in step 320 toselect accounts the she would like to access using system 100. The useris presented a list of her accounts/relationships with the institutionand is prompted to select “products” she wishes to web-enable. The listof relationships is presented to the user in the form of a checkbox listwith product names, and partial account numbers. After selectingaccounts to activate, the user is presented any associated legalagreements and further authentication and verification of ownershipquestions, based on the products/services she has chosen and theplacement of the products in the verification hierarchy. Theauthentication process is described in more detail below.

In addition to providing access to accounts, the customer is also ableto access services that are associated with the selected accounts. Forexample, a wire transfer capability is presented if the customer hasselected a DDA (checking) account. The reason that these services arepresented separately is that they may 1) be available only to certainproducts and 2) may have fees associated with their selection or 3) mayhave a special legal agreement or registration process associated withit. As a result, the customer cannot be given automatic rights to theservice.

The final step in the sign up process is the log on step 325. After theuser completes the activate accounts process of step 320, the userreceives a welcome and confirmation screen and is prompted to log on toaccess their accounts. At the same time, a request to generate and mailan Enrollment Verification Letter (EVL) to the user's home address onrecord is sent to the back office of the institution. This letterprovides an out-of-band notification that the user has been enabled toaccess and transact on their accounts online and is used to discoverfraud attempts if someone other than the customer has obtained knowledgeof the identification and verification of ownership data. The userreceives this EVL once, i.e. the very first time he signs up (not duringsubsequent enabling of accounts). In addition to the letter, thecustomer is sent a real-time email (if an email address was provided instep 305), which will confirm his enrollment.

FIG. 4 depicts in more detail the ownership verification process. Inorder to enable access to view or transact against accounts, a customermust undergo an ownership verification as is illustrated in FIG. 4. Thisownership verification process is used by both new and registered usersto verify ownership of an account whenever a customer attempts to “show”accounts that require a higher level of verification than what shecurrently has.

As previously described, verification for online access is based on ahierarchy of products within the institution. Customers who verifyownership (correctly answer questions for a particular product) areverified authenticated for each of the products below it in thehierarchy. For example, individuals who enable their checking andmortgage accounts for online access are verified with questions based ontheir Checking account, since checking is at a higher level in thepreferred product verification hierarchy defined by the institution. Ifthe same customer later decides to enable their credit card accountonline, they must answer additional questions, since the credit cardaccount is higher in the hierarchy than the customer's current level ofverification. By the same token, if the customer later chooses to enablehis auto loan account he is not required to answer any furtherverification questions since his current level of verificationsupercedes that required by auto loans.

Verification according to the present invention is different from theprior art authentication for several reasons. First, some of the priorart verification questions are not applicable to the Internet channel orto the “self-service” methods of the present invention. For example, aquestion related to a “a recent transaction” cannot be prompted andverified by a system such as system 100 in real time. The verificationquestions of the present invention relate to access to accounts via theInternet Channel, and are not related to a global name or addresschange.

Prior to entering the verification process of the present invention, theuser must have accepted the acknowledgment(s) and or agreement(s) forall product types for which the system is attempting to verify thecustomer (see step 315). Once ownership is verified, the verificationlevel and date are updated on the user's profile in the database of thesystem 100. If the user was directed to the verification screen becauseshe was requesting access to a new account, the user is returned to theselect accounts screen (see step 320 in FIG. 3).

Of the products the customer has chosen to activate online during theselect account process (step 320 of FIG. 3), an account of the “highest”product type on the hierarchy is chosen to verify against. If multipleaccounts of this product type have been selected, the system performsthe following logic to determine which account to use for product-levelverification. If the product type for verification is the same type thatthe user identified himself with during sign up/identification, theaccount number chosen during identification is used. If the product typewas not used for identification, then the first account returned on thelist is used.

In step 400 it is determined if the authentication level for the currentproduct/account selected is greater than the current level ofverification performed by the user. If it is not, the process proceedsto step 425 in which the user is confirmed for the present level ofverification. In a preferred embodiment of the present invention thehierarchy implemented for personal customers (as opposed to businesscustomers) is: Credit Card; Checking/MMA (excluding IRA MMA);Savings/IRA MMA/IRA Savings; CD/IRA CD; Overdraft Line of Credit;Investments; and Mortgage. The customer's SSN is not used forverification of a product since the user has already entered it duringthe Sign Up/Identification process. If a higher level of verification isrequired, the system, in step 405 checks to see if there is a completerecord for the account in the database of system 100. If there is not acomplete record, an error message is generated in step 407.

In step 410, the user is presented with a list of fields and asked toenter verification of ownership information based on the specificaccount selected from the hierarchy. All verification fields presentedto the user are required to be filled out. The user iterates through thescreen of verification questions until all fields are entered. (Notethat this data is validated only for completion at this point and is notyet compared to the database). System 100 notifies the user as to whichrequired fields are missing, if any. System 100 refers to the productsection for the verification questions to be asked for each product. Instep 415, system 100 verifies that all of the fields have valid data. Ifthere is invalid data (e.g., a missing digit in an account number) anerror message is generated in step 417 and the user has the chance tofix the data.

Once all mandatory fields are entered, the user has three attempts tomodify the verification information before the verification of ownershipprocess is halted (step 420). For security reasons, when information isincorrect, the specific field will not be highlighted. A generic messageis used, such as “Verification failed. Please try again.” Once the userhas successfully verified, the verification is confirmed in step 425 andthe user is able to then log on (step 430). The user's profile isupdated with the “new” verification level and date and a log transactionis created.

If the user is not able to present accurate information forauthentication after three tries in step 420, it is determined whetherthe user has provided enough information for authentication for at leastone product/account. If she has, the confirmation of step 425 isfollowed. If there is insufficient authentication for any product anerror message is displayed in step 435 and the authentication processesis exited in step 440.

The following are some examples of the verification questions requiredfor access to specific accounts. For credit card products, it isrequired that the user enter the trailing 4 digits for all of theaccounts they are selecting to “show”. If the user incorrectly entersthe trailing digits for the account being used for verification, then,after three attempts, the user fails verification altogether. However,if the user incorrectly enter the trailing 4 digits for an account notbeing used for verification, then the user just does not have onlineaccess to that account. In addition to the account number, the user willbe prompted to answer questions related to the following: Mother'sMaiden Name; the CVV/C2 number printed on the reverse side of thephysical credit card; Date of Birth; and Home Phone Number.

If the user's highest account in the product hierarchy is the checkingequivalent product account or if the user has a credit card withincomplete information and he has a checking account, the followinginformation is required for verification. Checking equivalent accountsinclude accounts such as a Money Market Account (MMA). The verificationinformation required for access to a checking account includes:. Accountnumber, Mother's Maiden Name; Transaction Amount (e.g., exact amount oflast withdrawal); Posting Date (of last transaction); Last DepositAmount; and Last Deposit Date.

If the user's highest account in the product hierarchy is the checkingequivalent product account or if the user has a credit card withincomplete information, he does not have a checking account and he has asavings account, the following information is required for verification.Savings equivalent accounts include a complete savings family ofSavings, IRA MMA, and IRA Savings accounts. The verification informationrequired for access to a savings account includes: Account number;Mother's Maiden Name; Last Deposit Amount; Last Deposit Date;Transaction Amount (e.g., Withdrawal); and Posting Date.

If the user's highest account in the product hierarchy is theCertificate of Deposit (CD) equivalent product account or if the userhas a credit card with incomplete information, he does not have achecking or savings account and he has a CD account; the followinginformation is required for verification. CD equivalent accounts refersto a complete CD family of CDs and IRA CDs. The verification informationrequired for access to a CD account includes: Account number; Mother'sMaiden Name; Date Opened; Original Principal Amount; Maturity Date; andPosted Interest.

If the user's highest account in the product hierarchy is an investmentaccount, auto loan, personal installment loan, home equity loan, ormortgage, and the customer identified themselves in step 305 with thataccount, the customer is not presented with verification questions inthe preferred embodiment since the business requirement is that thecustomer verify themselves using only a social security number and anaccount number. If they did not identify themselves in step 305 with thehighest account in the verification hierarchy, the customer is requestedto complete the account number of the account which is at the highestlevel.

The verification of ownership processes for online access for SmallBusiness customers is dependent on whether or not the customer has adeposit product in their profile. As with personal authentication, if abusiness customer verifies or correctly answers questions for aparticular product, they are automatically verified for each of theproducts below it in the hierarchy. Verification requirements for SmallBusiness customers differs from that for Personal customers. Productsavailable for online access are Checking, MMA, Savings, CD, Credit Card,Revolving credit products and Investments. As a rule, a businesscustomer must either verify ownership against a deposit account or aninvestment account. In a preferred embodiment, small business customerswill not be able to verify against any other accounts. In the preferredembodiment, the verification hierarchy for small businesses is asfollows: Checking/MMA; Savings; CD; and Investments.

As a result of the aforementioned rules, a business customer in thepreferred embodiment will only be able to verify ownership against theirDeposit or investment accounts for online access. Once verified, thecustomer can access all the products below the deposit account in thehierarchy.

Although described briefly before, the following generally describes thelog on process. When a user logs on, several scenarios exist based onvarying ID and password combinations inputted by the user such as validID/invalid password, invalid ID/invalid password, etc. Although each ofthese scenarios is a bit different, it has been learned that if thescenarios are treated differently, the system 100 will revealinformation regarding a “hit” on a valid ID, as well as informationregarding the security, and authentication logic and User ID statuswithin the system. To ensure that system 100 does not leak any suchinformation, all scenarios with regard to invalid ID/PW combinations aretreated identically. The customer has the ability to click on a “HavingTrouble?” link and be presented with Help options (that is, contactcustomer support or re-authenticate online options).

If the user types in a valid ID/valid Password combination, the system100 logs the user in successfully. If the user types in a valid ID buthas used the same ID for three consecutive log on attempts (notnecessarily in the same session) and this is a valid ID, system 100locks the user out. A User ID is locked after three (3) unsuccessful logon attempts with invalid passwords over an infinite number of dayswithout a successful log on. A counter within system 100 tracks thenumber of unsuccessful log ons. This counter is reset upon successfullog on. Once a User ID is locked, it will remain locked indefinitelyuntil the user re-authenticates online or calls Customer Support.(Customer Support has a function to unlock IDs) Even though a User ID is“locked”, the user will not see any change to the logon screen. The samelogon screen will continue to appear regardless of the number offailures. The user is not told that the User ID has been locked. Thereis a link titled “Having Trouble?”, which when clicked, instructs theuser to contact Customer Support or Re-authenticate online.

If the user types in an invalid ID and an invalid password, system 100provides a global parameter to detect this situation by sending an alertmessage to a pre-defined list of administrators when there have been,for example, 1000 failed log on attempts in 5 minutes. Due to thesecurity risk of information leakage if a different screen is presented,this user will not see any change to the log on screen, but will see thesame “Having Trouble?” link.

As seen above, in the simplest case, the user logs on successfully andgoes to the Account Summary page to view their accounts. However, thereare several other situations that must be accounted for, such as a userexceeding the maximum number of consecutive log on attempts (using thesame ID), the user has forgotten his password, or the user has receiveda pre-expired password in the mail and is attempting to log on.

If the user forgets his password or his ID, he can re-authenticatehimself to the system using the procedures described above with respectto challenge questions. An additional feature of the present inventionis the use of “cue” questions. As part of the initial sign on process,or at a later time, the user is able to cue questions that provide theuser with a hint as to the user's selected password. For example, if theuser selects the name of his dog as his password, the customer cancreate a cue question such as “What is your dog's name.” If the userforgets his password, he is first presented with the cue question to seeif the user can recollect the password. If the cue question does not jogthe user's memory, he is then presented with the above describedchallenge questions that allow the user to re-identify himself to thesystem.

After a user has successfully logged on, the user's profile is scannedfor any accounts for which the user has not accepted associated legalagreements. In addition, if a legal agreement has been updated and Legaldetermines that all users must be re-disclosed, such disclosures arepresented to the user again for acceptance. Access is not granted to aproduct type until all required legal agreements have been accepted.

The log on function also takes into account the fact that a user willnot automatically be going to the Account Summary page. Prospects(non-customers) sign up to system 100 to utilize a function other thanseeing account information. When a Prospect or a customer coming fromanother process than account access completes the sign up process, sheis directed to Log On. Upon a successful Log On, this user is thenreturned to the proper process. For example, if a user is coming fromanother process, the user is returned to this process instead of beingtaken to the Account Summary page. For example, a user might befollowing a URL to see the status of an online application for amortgage account. This page is protected, thus requiring the user to LogOn before being presented with the page that contains the customer'spersonal information. Upon a successful logon, the user should bebrought directly to the page she requested.

The log on process also presents the opportunity to collect challengequestions from current customers if they have not already done so. Upona successful logon, the user is prompted to select and answer challengequestions. As previously described, these questions replace theverification of ownership using account information. The user selectsone question from each of three drop down lists and completes theanswers. Since these are all customers of the institution, they willhave the option to opt-out of challenges. If they choose to do so, theywill not be able to re-authenticate online and create a new password.They would have go through the help center and a new password is mailedto them.

One of the significant features of the present invention is the abilityfor a customer to re-authenticate himself or herself to system 100, suchas in the case of a forgotten password or user ID. Typically a user isdirected to the re-authentication page from the log on screen, when theuser has unsuccessfully tried to log on. Successful re-authenticationallows the user to subsequently change his password. The “new” passwordis not validated against the “old” password to verify that they aredifferent—thus, a user who has hit the maximum failed log on attemptscan “reset” his password to the same password. At this point, the useris taken back to the Log On page.

For re-authentication, users will be presented with two of the three“challenge” questions that were originally created during sign up or logon as previously described. The user answers to these questions duringreauthentication must match the answers they previously provided. In apreferred embodiment, if the user unsuccessfully attempted tore-authenticate online 9 number of times in the last 30 days, the userwill not have the ability to change their password online. These usersare stopped before challenge questions are presented and given an errormessage instructing them to call customer service. For example, the usercan only try and re-authenticate during 3 sessions in 30 days.

If a user is eligible to re-authenticate online using challengequestions, system 100 randomly selects two of the three challengequestions and presents them to the user. The user has threeopportunities to answer these questions. If they do not pass after threeattempts, the user is directed to an error screen. If the usersuccessfully answers these questions, they are then able to change theirpassword online.

As previously described in relation for FIG. 1, the purpose of thesign-up, log on and verification procedure is to allow customers to viewall of their accounts with the institution though a single interfacewith a single sign on process. The account summary page of the presentinvention summarizes all of the accounts in a balance sheet format thatthe customer has selected to “show” and for which the customer has beenverified. Each account that the user has selected to “show” for onlineaccess is displayed on this screen under either the “Deposit”, “CreditCard and Revolving Credit”, or “Mortgage and Loans” main heading. Whenthe user clicks on a specific account to view details, he enters thesystem for the specific line of business (LOB) (see 190-196 in FIG. 1).

On the account summary screen, the user is presented with a list oftheir enabled accounts, from which they can make a selection to see moredetails. They make their selection by clicking on the relevanthyperlinks, which brings the user into the appropriate LOB sitesupporting the selected product/account. For example, the supporting LOBsite could be online banking, mortgage servicing, investment or tradingor credit card servicing. This screen also contains summary (balance)information for each of the accounts presented to the customer. Thisinformation will vary depending on the type of account.

When the user comes to the account summary screen, system 100 uses thecustomer profile to determine which accounts to display on the summaryscreen. The user's accounts are validated with the respective LOB systemonce per session. The validation consists of verifying that the accountstill exists and that this status is still valid. In the case of aninvalid status or account that no longer exists, a pop-up windowinstructs the user that account has been removed from his onlineportfolio and provide the phone number for customer service. The accounttitle and account number (with certain digits masked) are displayed forall enabled accounts. The account summary (balance) information for eachof the accounts is displayed to the customer. Like the account statusinformation, this information is refreshed once per session.

Other options available to the customer from the account summary screeninclude the ability to maintain their user profile. This includesmaintenance of the e-mail address entered in the sign up process or in aprevious maintenance session, changing a password (once the old passwordis entered), changing challenge questions, adding personal loans totheir business online profile or selecting or deleting accounts fromtheir online profile. The selection of accounts is available because thecustomer may have previously failed the verification of ownership of theaccount, the account has been originated since the customer signed upfor online access, or the account now has web-enabled access.

When adding additional accounts to their online profile, the level ofhierarchy previously verified is compared against the highest level ofthe accounts selected for addition. If the requested accounts are loweror equal to the verification level, the accounts are automaticallyenabled in the customer's online profile. If the requested accounts arehigher than the previously passed hierarchy level, the verificationquestions related to the highest of the requested accounts are presentedto the customer for completion. In this case, the requested accounts arenot added to the customer's online profile until they successfully passthe verification of ownership questions.

Although the present invention has been described in relation toparticular embodiments thereof, many other variations and other useswill be apparent to those skilled in the art. It is preferred,therefore, that the present invention be limited not by the specificdisclosure herein, but only by the following claims.

1-54. (canceled)
 55. A method for accessing a plurality of service provider systems across a network through a host service provider using a single sign on, the method comprising: a host service provider receiving validation information from a user; the host service provider retrieving data from a validation database, based on the validation information from the user, wherein the data is effective for accessing at least one service provider system and is based at least in part on the validation information from the user; transmitting the data to at least one of the service provider systems; and directing the user to at least one of the service provider systems such that the user accesses information at the at least one of the service provider systems.
 56. The method of claim 55, the validation information including a received user ID and password.
 57. The method of claim 55, wherein the host service provider is in the form of an application server.
 58. The method of claim 55, wherein the validation database includes a database that contains customer profiles.
 59. The method of claim 58, wherein the customer profiles include user IDs, passwords, relationship data and profile data.
 60. The method of claim 58, the customer profiles are maintained in the database in the form of a customer identification file (CIF).
 61. The method of claim 55, wherein at least one of the service provider systems is a line of business system.
 62. The method of claim 55, wherein each of the plurality of service provider systems is a line of business system.
 63. The method of claim 55, where the service provider systems and the host service provider communicate with the user over the Internet.
 64. The method of claim 55, further comprising performing processing to sign the user up with the host service provider.
 65. The method of claim 64, the processing to sign the user up with the host service provider including performing processing to register the user with a user's account.
 66. A system for accessing a plurality of service provider systems via a single sign on to a host service provider, the system comprising: a plurality of service provider systems; a data communication network; a host service provider for receiving the single login from a user and selectively directing the user to at least one of the service provider systems, the host service provider in communication with the service provider systems and the user over the data communication network, and the single login including validation information of the user; and a validation database for storing stored information for accessing the plurality of service provider systems, the host service provider retrieving the stored information from the validation database, and the host service provider comparing the stored information with the validation information received from the user so as to determine access to the plurality of service provider systems.
 67. The system of claim 66, the validation information including a user ID and password.
 68. The system of claim 66, the host service provider being in the form of an application server.
 69. The system of claim 66, the validation database including a database that contains customer profiles.
 70. The system of claim 66, further including a middleware component, the middleware component providing for communications between the host service provider and the service provider systems.
 71. The system of claim 70, the middleware component including a communication server and a delivery processor.
 72. The system of claim 66, each of the plurality of service provider systems is a line of business system.
 73. The system of claim 66, further including a customer workstation to interface with the customer, the customer workstation being in communication with the host service provider over a communication network, the communication network being the Internet.
 74. The system of claim 73, the customer workstation supporting an Internet browser, the Internet browser providing the communication with the host service provider.
 75. The system of claim 66, the validation database further storing information for signing up the user with the service provider systems.
 76. The system of claim 66, wherein the host service provider, based on the stored information from the validation database, determining which of the service provider systems the user is provided access to.
 77. The system of claim 66, wherein the host service provider provides access to account information pertaining to a plurality of the user's accounts, the account information of the plurality of accounts residing respectively in the plurality of service provider systems.
 78. The system of claim 77, wherein access is provided, by the host service provider, to the accounts based on a hierarchy ranking, the host service provider determining a highest level account to which the user is entitled access, based on the stored information, and the host service provider providing access to all accounts at and under such highest level account.
 79. A method for accessing a plurality of separate service provider systems across a network through a host service provider, the method comprising: a host service provider receiving validation information from a user, the validation information including a user ID and a password; the host service provider retrieving data from a validation database, based on the validation information from the user, wherein the data is effective for accessing a plurality of service provider systems and is based at least in part on the validation information from the user; transmitting the data to a selected one of the service provider systems; and directing the user to the selected one of the service provider systems such that the user accesses information at the selected one of the service provider systems; the host service provider providing the user with a listing corresponding with the plurality of service provider systems, the listing based on the data from the validation database; the host service provider providing registration processing for registering further users such that the further users are provided access to accounts of the further users, the providing registration processing including: prompting a further user to create a user identification; prompting the further user to create a password; and establishing the further user identification and password with respect to the further user, wherein the creation and establishment steps occur online; and wherein the creation and establishment steps occur during a single online session; wherein the data in the validation database includes information regarding the profile of the user; wherein the user is an individual; and wherein the service provider systems and the host service provider communicate with the user over the Internet.
 80. The method of claim 79, wherein the listing corresponding with the plurality of service provider systems includes at least one of account information and services information.
 81. The method of claim 79, wherein the listing corresponding with the plurality of service provider systems includes financial services related account information, the account information including balance information.
 82. The method of claim 79, wherein the directing the user to the selected service provider systems such that the user accesses information at the selected service provider systems includes transferring the user such that the user enters the selected service provider system.
 83. The method of claim 82, wherein the selected service provider system provides for the effecting of transactions by the user. 